Skip to content

Conversation

@Sandesh282
Copy link

Description

This PR introduces a comprehensive guide to the Python Pandas library. It covers the basics of Series and DataFrame, data input/output operations, and basic data analysis. The motivation is to provide a starting point for ML/DS workflows at Recode Hive, where no official documentation for Pandas currently exists.

Fixes # (issue)

Type of Change

  • New feature (e.g., new page, component, or functionality)
  • Bug fix (non-breaking change that fixes an issue)
  • UI/UX improvement (design, layout, or styling updates)
  • Performance optimization (e.g., code splitting, caching)
  • Documentation update (README, contribution guidelines, etc.)
  • Other (please specify):

Changes Made

  • Added a new Markdown page introducing Pandas.
  • Included explanations of Series and DataFrame structures.
  • Added sections for data input/output and basic data analysis operations.
  • Provided rationale for introducing Pandas to the project documentation.

Dependencies

  • No new dependencies required.
  • Compatible with the existing Python/ML workflow documentation.

Checklist

  • My code follows the style guidelines of this project.
  • I have tested my changes across major browsers and devices.
  • My changes do not generate new console warnings or errors.
  • I ran npm run build and attached screenshot(s) in this PR.
  • This is already assigned Issue to me, not an unassigned issue.

@vercel
Copy link
Contributor

vercel bot commented Oct 26, 2025

Someone is attempting to deploy a commit to the recode Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions github-actions bot added hacktoberfest-accepted recode this is label for leaderboard labels Oct 26, 2025
@github-actions
Copy link

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. The estimated time for response is 5–8 hrs.

In the meantime, please provide all necessary screenshots and make sure you run - npm build run , command and provide a screenshot, a video recording, or an image of the update you made below, which helps speed up the review and assignment. If you have questions, reach out to LinkedIn. Your contributions are highly appreciated!😊

Note: I maintain the repo issue every day twice at 8:00 AM IST and 9:00 PM IST. If your PR goes stale for more than one day, you can tag and comment on this same issue by tagging @sanjay-kv.

We are here to help you on this journey of open source. Consistent 20 contributions are eligible for sponsorship 💰

🎁 check our list of amazing people we sponsored so far: GitHub Sponsorship. ✨

📚Your perks for contribution to this community 👇🏻

  1. Get free Consultation use code recode50 to get free: Mentorship for free.

  2. Get the Ebook for free use code recode at checkout: Data Science cheatsheet for Beginners.

  3. Check out this weekly Newsletter: Sanjay's Newsletter.

If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

@steam-bell-92
Copy link
Member

@Sandesh282 This issue was not assigned to you, it is assigned to me. Please close this PR

@sanjay-kv
Copy link
Member

need to add into sidebar.tx file

@sanjay-kv sanjay-kv added the under review Review under the maintainers or the admins label Oct 27, 2025
@sanjay-kv sanjay-kv moved this to In Progress in @recode-web Oct 27, 2025
@steam-bell-92
Copy link
Member

Hi @sanjay-kv ,

As the assigned contributor for issue #1082, I must point out a critical process issue: PR #1084 was raised before any assignment was made, which is a direct violation of the contribution rule: "Don't raise PR unless assigned to you."

As a regular contributor, I am committed to following the process and delivering the highest quality work. My assigned plan for #1082 outlines a better, structured solution (multiple, detailed sections) that is good for the long-term documentation.

To maintain project quality and adherence to the guidelines:

Could you please close this non-compliant PR so I can immediately proceed with my assigned and structured solution for #1082?

@iitzIrFan
Copy link
Member

@steam-bell-92 Made a valid point here

Hi @sanjay-kv ,

As the assigned contributor for issue #1082, I must point out a critical process issue: PR #1084 was raised before any assignment was made, which is a direct violation of the contribution rule: "Don't raise PR unless assigned to you."

As a regular contributor, I am committed to following the process and delivering the highest quality work. My assigned plan for #1082 outlines a better, structured solution (multiple, detailed sections) that is good for the long-term documentation.

To maintain project quality and adherence to the guidelines:

Could you please close this non-compliant PR so I can immediately proceed with my assigned and structured solution for #1082?

@steam-bell-92 made a valid point here. @Sandesh282 , I understand you may want to complete a few more PRs before Hacktoberfest ends, but I would like to emphasize that the FOSS community values meaningful contributions over quantity.

I would suggest closing this PR and exploring other open issues in the repository. I would be happy to review those. Also, to maintain proper workflow, we only review PRs from contributors who are assigned to the corresponding issues. Thanks for understanding!

C.C @sanjay-kv

@iitzIrFan iitzIrFan added the don't-merge faced conflict issue or other dev related issue, dont merge PR label Oct 27, 2025
@iitzIrFan iitzIrFan moved this from In Progress to Backlog in @recode-web Oct 27, 2025
@Sandesh282 Sandesh282 closed this Oct 27, 2025
@github-project-automation github-project-automation bot moved this from Backlog to Done in @recode-web Oct 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

don't-merge faced conflict issue or other dev related issue, dont merge PR hacktoberfest-accepted recode this is label for leaderboard under review Review under the maintainers or the admins

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants